docs(changelog): platform token spend now actually bills#89
Merged
Conversation
User-facing entry for the runner split-token billing fix: platform-model runs were charged run-fee-only because the runner never reported its token counts; it now streams cumulative input/output counts on every renewal and the final report. Documents the renew/report body shape, the zero-default wire compatibility (mixed fleet safe both directions), and the cached-input 0 limitation until the provider layer surfaces cache reads. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
…tile P1/P2) The API reference block documented the /v1/runners/me/* renew/report wire shape — internal runner↔control-plane RPC, which AGENTS.md keeps out of operator docs. Removed it and softened the lead to drop the empty-body/field-shape specifics; the user-facing story (platform token spend now bills; update your runner fleet) and the cached-input caveat stay. Removing the API reference section also fixes the section-order inversion (Bug fixes had preceded API reference). Dropped the now-unused "API" tag. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changelog entry for usezombie#399 — the runner split-token billing fix.
Platform-model runs were charged run-fee-only because the runner never reported its token counts; it now streams cumulative input/output counts on every renewal and the final report. The entry documents the renew/report body shape, the zero-default wire compatibility (mixed fleet safe both directions), and the cached-input-0 limitation.
Decoupled from the binary VERSION per the changelog convention (date label, no semver prefix). Distinct Jun 12 block from the M91 memory-observability entry already on main.
🤖 Generated with Claude Code
Greptile Summary
Adds a changelog entry for the runner split-token billing fix: platform-model runs previously settled token spend at zero because the runner never reported token counts; it now does, so the token component of every platform run bills correctly going forward.
<Update>block (Jun 12, 2026, "Bug fixes") explains the under-billing root cause, instructs operators to upgrade their runner fleet, and notes the cached-input limitation.Upgrading → Bug fixessection order,MMM DD, YYYYdate label, no semver prefix, and no runner RPC wire-format internals exposed.Confidence Score: 5/5
Documentation-only change with no executable code; safe to merge.
The change adds a single changelog entry. Section order, date format, terminology, and content boundaries all conform to AGENTS.md. The previous concerns about section ordering and internal RPC protocol exposure are no longer present in this version. No operator-visible behavior changes.
No files require special attention.
Important Files Changed
<Update>block documenting the runner token-billing fix; section order, date format, and terminology all conform to AGENTS.md conventions.Sequence Diagram
sequenceDiagram participant Runner participant ControlPlane as Control Plane participant Billing Note over Runner,Billing: Before fix — token counts never reported Runner->>ControlPlane: POST /renew (no token fields) ControlPlane->>Billing: "Charge run-fee only (token_count = 0)" Note over Runner,Billing: After fix — cumulative counts streamed Runner->>ControlPlane: POST /renew (input_tokens, output_tokens) ControlPlane->>Billing: Charge run-fee + token component Runner->>ControlPlane: POST /report (final input_tokens, output_tokens) ControlPlane->>Billing: Final token reconciliation Note over Runner,ControlPlane: Older runner (zero defaults) Runner->>ControlPlane: POST /renew (no token fields → default 0) ControlPlane->>Billing: Charge run-fee only (backward compatible)Reviews (2): Last reviewed commit: "docs(changelog): keep token-billing entr..." | Re-trigger Greptile
Context used: